Task: Verify system design
To ensure the system and the HW-SW design comply with the technical safety concept
Purpose
To show that the technical safety concepts that have been developed are workable for the system design proposed.
Relationships
RolesPrimary: Additional: Assisting:
InputsMandatory: Optional:
  • None
External:
  • None
Outputs
Main Description

The task of the system design verification  is split into three stages the first stage is an inspection or walkthrough (depending upon the ASIL of the item being verified). the second stage is verification through simulation and or vehicle test/ systems prototyping, the final stage is verification of the systems safety analysis.

This information is contained in ISO 26262 vol 4, clause 7.4.8.1 in the Table 3 System Design Verification, the intent is capture in the steps detailed for this sub phase.

If system based modeling is used, simulation is possible based upon using  the verification task from Architectural Design - Use-Case based. These techniques can also be used as a method for fault injection. Another aspect of verify the safety of the system design is through timing analysis, if an MBSE approach has been adopted this can be carried out using the INCHRON tool ChronSim in conjunction with Rhapsody

Safety Analyses as detailed in Develop technical safety concept step 2 and in ISO 26262, vol 9, clause 8.

If the result of this verification procedure is that new hazards are identified that are not part of the safety goal then these new new hazards are analyzed as per the standard safety lifecycle workflow. The user is referred to ISO 26262, vol 4 clause 7.4.8. for guidance.






Steps
Verify System design trhough review

This process is intended to check that the technical safety requirements have been detailed and implemented correctly in the design. The two means to achieve this are

System design inspection, which is recommended for items with an ASIL of A and highly recommended for items with an ASIL of B,C or D

System design walkthrough, which is recommended for items with an ASIL of B and highly recommended for items with an ASIL of A, with an unbiased opinion on its usage for items of ASILs C or D

This information is a part summary of the information taken from ISO 26262 vol 4 clause 7.4.8.1 table 3- System design verification.

Real time verification of behaviour and constrainst

The the intent of this phase is to ensure that the item behaves as expected when introduced into a virtual or real environment. These phase of verification provides a useful means for testing using fault injection techniques.

Simulation is highly recommended for items of ASIL of C or D and recommended for items of ASIL of A or B.

System prototyping and vehicle tests  are highly recommended for items of ASIL of C or D and recommended for items of ASIL of A or B.

This information is a part summary of the information taken from ISO 26262 vol 4 clause 7.4.8.1 table 3- System design verification.

Verify System design through safety analysis

The safety analysis techniques to be used are dependent upon the ASIL of the item being developed, in this instance two types of technique are employed. Deductive and Inductive, there applicability to items of a specific ASIL are detailed below.

Inductive methods such as FMEA, ETA and Markov modeling are highly recommended for items with any ASIL level.

Deductive methods such as FTA and reliability block diagrams are highly recommended for items with an ASIL of C or D, whilst these methods are recommended for items with an ASIL of B,  there is no recommendation for against or the usage of these techniques for items with an ASIL of A.

This information is a part summary of the information taken from ISO 26262 vol 4 clause 7.4.8.1 table 3- System design verification.


Properties
Predecessor
Multiple Occurrences
Event Driven
Ongoing
Optional
PlannedYes
Repeatable
Key Considerations

Practices applicable to help with the verification of the system design.

More Information